home *** CD-ROM | disk | FTP | other *** search
/ Columbia Kermit / kermit.zip / newsgroups / misc.19970929-19971216 / 000008_news@newsmaster….columbia.edu _Mon Sep 29 23:23:26 1997.msg < prev    next >
Internet Message Format  |  2020-01-01  |  2KB
  1. Return-Path: <news@newsmaster.cc.columbia.edu>
  2. Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
  3.     by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id XAA20562
  4.     for <kermit.misc@watsun.cc.columbia.edu>; Mon, 29 Sep 1997 23:23:26 -0400 (EDT)
  5. Received: (from news@localhost)
  6.     by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id XAA28576
  7.     for kermit.misc@watsun; Mon, 29 Sep 1997 23:23:25 -0400 (EDT)
  8. Path: news.columbia.edu!panix!howland.erols.net!cpk-news-hub1.bbnplanet.com!news.bbnplanet.com!News1.Ottawa.iSTAR.net!News4.Toronto.iSTAR.net!News1.Vancouver.iSTAR.net!news.istar.net!cal.istar!news
  9. From: Russell Magee <bigruss@cheetah.spots.ab.ca>
  10. Newsgroups: comp.protocols.kermit.misc
  11. Subject: Re: How, exactly, should Kermit encode data?
  12. Date: 30 Sep 1997 03:21:49 GMT
  13. Organization: iSTAR internet Incorporated
  14. Lines: 24
  15. Message-ID: <60pr8d$423@nr1.calgary.istar.net>
  16. References: <60ko7e$pts@nr1.calgary.istar.net> <60oeb7$fc3$1@apakabar.cc.columbia.edu>
  17. NNTP-Posting-Host: cheetah.spots.ab.ca
  18. X-Newsreader: TIN [UNIX 1.3 unoff BETA 970709; i586 Linux 2.0.29]
  19. Xref: news.columbia.edu comp.protocols.kermit.misc:7771
  20.  
  21. Frank da Cruz <fdc@watsun.cc.columbia.edu> wrote:
  22. > : 
  23. > I don't know what Kermit protocol spec you found on what ftp site, but no
  24. > reverse engineering was necessary; the Kermit protocol is specified in the
  25. > book "Kermit, A File Transfer Protocol":
  26.  
  27. >   http://www.columbia.edu/kermit/manuals.html
  28.  
  29. > - Frank
  30.  
  31.   The document I got was "Kermit, a Simple File Transfer Protocol
  32. for Microcomputers and Mainframes", by yourself and a Mr. Bill Catchings.
  33.   I'm sure this isn't the most up-to-date document (1983), but I didn't
  34. have much time for research unfortunately 8-/. I will definitely have to
  35. pick up that book though. I didn't mean to imply that I had to reverse-
  36. engineer the Kermit protocol; the doc actually seemed quite clear.
  37.   As someone has already told me in email, Telix's implementation of Kermit
  38. may very well be broken.
  39.  
  40.  
  41.   Thanks for the book reference.
  42.  
  43.   -Russ
  44.